Quick question, I have a Laravel 5.6 site using socialite. When I run a composer update I am getting v3.2.0 which does not have the updates from this pull request I'm curious about the best way for me to be prepared for the Google+ API being shutdown. Is the plan to merge these changes into a new tag, such as v3.3.0 so that I can simply do a composer update and expect things to work or should I update composer json to specifically make use of the 3.0 branch. Looking at v3.2.0...3.0 it seems that there are other changes that have not been pulled into latest tagged version and thus excluded from being implemented on my site (if I am understanding the proper flow of things).

@arborrow you can require 3.0.x-dev https://packagist.org/packages/laravel/socialite#3.0.x-dev

@driesvints thanks, specifying 3.0.x-dev in composer.json worked perfectly. Just for the sake of documentation, I was checking the user's domain using the Google+ API user['domain']; however, the People API uses user['hd']. Once I cleaned up my references to domain to hd in my code everything else seemed to work just fine and I was able to disable the Google+ API.

@taylorotwell - please release this change google+ api change as next minor version so we can pull it through composer.

Anyways google+ api is shutting down, so its not gonna work.

@rajjanorkar please read my comment here: #319 (comment)